Bridge Status Reporter Service

Overview

Implements a service that polls External Adapter /status endpoints at configurable intervals and emits structured telemetry events via Beholder. Provides operational visibility into bridge health, configuration, and runtime state.

Implementation

Core Service (core/services/nodestatusreporter/bridgestatus/)

• bridge_status_reporter.go - Service implementation with polling loop, HTTP client, error handling

Protobuf Schema (events/)

Configuration Integration

• core/config/docs/core.toml - Added [BridgeStatusReporter] configuration section
• core/config/toml/types.go - Configuration struct and setters
• core/config/bridge_status_config.go - Configuration interface
• core/services/chainlink/config_bridge_status.go - Service configuration implementation

Features

Service Behavior

• Queries bridge registry on startup and at each polling interval
• Polls bridge URLs with configurable status path (default: /status)
• Continues operation when individual bridges fail
• Configurable filtering of bridges without jobs or with HTTP errors
• Graceful shutdown with context cancellation

Telemetry Data Structure

Emits BridgeStatusEvent containing:

• Bridge metadata: name, adapter name/version, uptime
• Runtime information: Node.js version, platform, architecture, hostname
• Endpoint definitions: names, aliases, supported transports
• Configuration parameters: name/value pairs, types, defaults
• Associated job information: external job IDs and names

Configuration

[BridgeStatusReporter]
Enabled = false                    # Default: false
StatusPath = "/status"            # Default: "/status"
PollingInterval = "5m"            # Default: "5m"
IgnoreInvalidBridges = true       # Default: true
IgnoreJoblessBridges = false      # Default: false

Usage

Node Operators

Configure service via TOML, ensure External Adapters implement status endpoints.

External Adapter Developers

Implement GET /status endpoint returning JSON with required fields, available in adapters using ea-framework-js v2.7.0+

Monitoring Systems

Consume BridgeStatusEvent messages via Beholder telemetry pipeline.